Make the return values of Client.transport_query() more Pythonic #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I want to rename
transport_query()totransport_query_struct()to still have a low-overhead way to get the information, which might probably even be somewhat realtime safe.Any suggestions for a better name?
Then I want to implement a new
transport_query()method which calls the oldtransport_query_struct()and prepares the results to be nicer to handle:jack.TransportStateclass to wrap the "state" integertransport_query()jack.ROLLING) to instances of this classjack_position_tstruct into a Pythondictthat only contains the valid information